Enhancing functionalities of virtual assistants and dialog systems via plugin marketplace

ABSTRACT

A method for enhancing dialog systems is disclosed herein. The method may include maintaining an online marketplace that may have a plurality of dialog system extension elements. The plurality of dialog system extension elements may include at least one of a dialog system plugin, a dialog system add-on, a dialog system update, and a dialog system upgrade. The method may further include receiving a selection of one of the plurality of dialog system extension elements from an end user. The end user may be associated with a dialog system. The method may continue with associating the one of the plurality of dialog system extension elements with the dialog system of the end user.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present utility patent application is related to and claims prioritybenefit of the U.S. provisional application No. 62/166,686, filed on May27, 2015, under 35 U.S.C. 119(e), which is incorporated herein byreference in its entirety for all purposes to the extent that suchsubject matter is not inconsistent herewith or limiting hereof.

TECHNICAL FIELD

This disclosure relates generally to dialog systems and virtualassistants and an online platform allowing end users of dialog systemsto customize or improve the dialog systems or the virtual assistantswith which the end users work. More particularly, this disclosurerelates to an online plugin marketplace for the online platform, inwhich an end user associated with a dialog system can extendfunctionalities of the dialog system.

BACKGROUND

Currently, dialog systems are widely used in the information technologyindustry, especially in the form of mobile applications for cell phonesand tablet computers. A dialog system can include a computer-based agenthaving a human-centric interface for accessing, processing, managing,and delivering information. Dialog systems are also known as chatinformation systems, spoken dialog systems, conversational agents,chatter robots, chatterbots, chatbots, chat agents, digital personalassistants, automated online assistants, and so forth. All these termsare within the scope of the present disclosure and referred to as a“Dialog System” for simplicity.

Traditionally, a dialog system interacts with its users in naturallanguage to simulate an intelligent conversation and providepersonalized assistance to the users. For example, a user may generaterequests to the dialog system in the form of conversational questions,such as “What is the weather like in Palo Alto?” and receivecorresponding answers from the dialog system in the form of audio and/ordisplayable messages. The users may also provide voice commands to thedialog system requesting the performance of certain functions,including, for example, generating e-mails, making phone calls,searching particular information, acquiring data, navigating, requestingnotifications or reminders, and so forth. These and otherfunctionalities make dialog systems very popular as the dialog systemsmay be of great help, especially for holders of portable electronicdevices such as smart phones, cellular phones, tablet computers, gamingconsoles, and the like.

Although the demand for dialog systems for third party mobileapplications and web services has been growing, it is not an easy taskto create a well-operating dialog system. Each dialog system may have adialog system interface and dialog system engine. The dialog systeminterface may be responsible for receiving user inputs and deliveringdialog system responses to the user. The dialog system engine may beresponsible for transforming voice user inputs into text inputs,interpreting text inputs, and generating corresponding responses to textinputs. The process running on the dialog system engine is also known as“natural language processing” (NLP). Development of NLP models is notonly very time consuming, but is also a highly technical task.Accordingly, currently existing dialog systems may be very different intheir capabilities. For example, a dialog system can properly work forgenerating emails and search information on the Internet, but the dialogsystem may not be properly configured to handle user requests related toscheduling events or booking hotel rooms. Additionally, some dialogsystems may well handle booking requests, but may be not able to addressgenerating email requests by end users. Therefore, many end users maywant to extend functionalities of the dialog systems with which theywork.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Provided is a system for enhancing functionalities of dialog systems.The system may include at least one processor and a memory. The memorymay be operable to maintain an online marketplace that may comprise aplurality of dialog system extension elements. The plurality of dialogsystem extension elements may include at least one of a dialog systemplugin, a dialog system add-on, a dialog system update, and a dialogsystem upgrade. The processor may be operable to receive a selection ofone of the plurality of dialog system extension elements from an enduser. The end user may have a dialog system associated with the enduser. The processor may be further operable to associate the one of theplurality of dialog system extension elements selected by the end userwith the dialog system of the end user.

Provided is a method for enhancing functionalities of dialog systems.The method may include maintaining an online marketplace that maycomprise a plurality of dialog system extension elements. The pluralityof dialog system extension elements may include at least one of a dialogsystem plugin, a dialog system add-on, a dialog system update, and adialog system upgrade. The method may further include receiving aselection of one of the plurality of dialog system extension elementsfrom an end user. The end user may be associated with a dialog system.The method may continue with associating the one of the plurality ofdialog system extension elements selected by the end user with thedialog system of the end user.

Additional objects, advantages, and novel features will be set forth inpart in the detailed description, which follows, and in part will becomeapparent to those skilled in the art upon examination of the followingdetailed description and the accompanying drawings or may be learned byproduction or operation of the example embodiments. The objects andadvantages of the concepts may be realized and attained by means of themethodologies, instrumentalities, and combinations particularly pointedout in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example and not limitation in thefigures of the accompanying drawings, in which like references indicatesimilar elements and, in which:

FIG. 1 illustrates an environment within which systems and methods forenhancing functionalities of dialog systems can be implemented, inaccordance with some embodiments.

FIG. 2 is a process flow diagram showing a method for creating dialogsystem engines, in accordance with example embodiments.

FIG. 3 is a block diagram showing various modules of a dialog systemengine, in accordance with example embodiments.

FIG. 4 shows a Graphical User Interface (GUI) for creating a dialogsystem entity, in accordance with an example embodiment.

FIG. 5 shows a GUI for creating a dialog system intent, in accordancewith an example embodiment.

FIG. 6 shows a GUI for creating a dialog system intent, in accordancewith an example embodiment.

FIG. 7 is a block diagram of a system for enhancing functionalities ofdialog systems, in accordance with example embodiments.

FIG. 8 is a flow chart illustrating a method for enhancingfunctionalities of dialog systems, in accordance with exampleembodiments.

FIG. 9 is a high-level block diagram illustrating an example user devicesuitable for implementing the methods described herein.

DETAILED DESCRIPTION

The following detailed description includes references to theaccompanying drawings, which form a part of the detailed description.The drawings show illustrations in accordance with example embodiments.These example embodiments, which are also referred to herein as“examples,” are described in enough detail to enable those skilled inthe art to practice the present subject matter.

The embodiments can be combined, other embodiments can be utilized, orstructural, logical and operational changes can be made withoutdeparting from the scope of what is claimed. The following detaileddescription is, therefore, not to be taken in a limiting sense, and thescope is defined by the appended claims and their equivalents.

Present teachings may be implemented using a variety of technologies.For example, the methods described herein may be implemented in softwareexecuting on a computer system or in hardware utilizing either acombination of microprocessors or other specially designedapplication-specific integrated circuits, programmable logic devices, orvarious combinations thereof. In particular, the methods describedherein may be implemented by a series of computer-executableinstructions residing on a transitory or non-transitory storage mediumsuch as a disk drive or computer-readable medium. It should be notedthat methods disclosed herein can be implemented by a computer (e.g., adesktop computer, a tablet computer, a laptop computer), a game console,a handheld gaming device, a cellular phone, a smart phone, a smarttelevision system, and so forth.

The terms “application developer,” “plugin developer,” “softwaredeveloper,” or simply “developer” refer to one or more of the following:a software developer, a mobile application developer, a softwareengineer, a software owner, a mobile application owner, a softwaremanager, a mobile application manager, a dialog system owner, and soforth. Application developers develop and/or manage a Dialog SystemEngine, a Dialog System Interface, and/or plugins.

The term “Dialog System” refers to one or more of the following: a chatinformation system, a spoken dialog system, a conversational agent, achatter robot, a chatterbot, a chatbot, a chat agent, a digital personalassistant, an automated online assistant, etc. Each Dialog Systemincludes a “Dialog System Interface” and “Dialog System Engine.” Each ofthese elements can be customized by an application developer.

The term “Dialog System Interface” refers to a computer-human interface,which is configured to acquire user inputs in the form of audio messagesor text messages, and deliver dialog system responses to the users inthe form of audio messages or displayable messages. In an exampleembodiment, a Dialog System Interface may be implemented as a widgetemployed to or integrated with a software application, a mobileapplication, a middleware application, a firmware application, awebsite, and web service, to provide a computer-human interface foracquiring user requests and delivering dialog system outputs to theusers.

The term “Dialog System Engine” refers to a software application, whichis configured to process user inputs and generates responses thereto. Inone example embodiment, a Dialog System Engine refers to acomputer-enabled or processor-enabled system for supporting anassociated Dialog System Interface by processing user requests andgenerating corresponding responses thereto.

The term “plugins” refers to one or more of the following: softwareplugins, add-ons, software extensions, updates, upgrades, or softwarecodes for a Dialog System Engine. The term “plugins” is also referredherein to as “dialog system extension elements.”

The present technology provides for a platform for maintaining multipleDialog System Engines serving as backend services for Dialog SystemInterfaces. The present technology also provides for an onlinemarketplace, such as the online marketplace implemented as a website orweb service, which may include a plurality of dialog system extensionelements, including various plugins, add-ons, extensions, updates, orsoftware codes allowing the enhancement of the functionality of DialogSystems maintained by the platform. For simplicity, “dialog systemextension elements” are referred to herein as “plugins.” In particular,the platform may maintain one or several Dialog System Engines beingcore Dialog System Engines and may maintain a plurality of plugins bywhich functionalities of the core Dialog System Engines may be expanded.

Dialog System Interfaces can be implemented at least as a part ofsoftware applications, mobile applications, middleware applications,firmware applications, websites, web services, and so forth. In otherwords, Dialog System Interfaces may be on a client side and may providea computer-human interface configured to at least acquire user inputsand deliver dialog system outputs to the end users. Dialog SystemEngines, on the other hand, may support the Dialog System Interfaces byprocessing user inputs and generating corresponding responses to theuser inputs. Thus, the Dialog System Engine, along with plugins for theDialog System Engine, and the Dialog System Interface, when interactingwith each other, form a Dialog System. One may refer to a Dialog SystemInterface running on or accessed from a client device as a “frontend”user interface, while a Dialog System Engine, which supports theoperation of such Dialog System Interface, can be referred to as a“backend” service.

In general, the online marketplace may maintain dialog system extensionelements for customizable Dialog System applications and customizableDialog Systems. The online marketplace can be a part of a developeronline platform for creating customizable Dialog Systems.

The technology of the present disclosure makes it easy and fast for endusers to improve and customize Dialog Systems for a wide range oferrands and tasks. The end users using Dialog Systems may have thepossibility to extend functionalities or capabilities of the DialogSystems by installing plugins and integrating the plugins into theDialog Systems. The plugins may be provided when purchased by the enduser or on a free-of-charge basis. In one example embodiment, the endusers may visit a website or web service associated with the onlinemarketplace and review available plugins and functions of the plugins.Each plugin can be supplemented with metadata, including descriptions,price, terms, publisher's information, ranks, reviews, and so forth. Inanother example embodiment, the Dialog Systems may allow the end usersto install certain plugins when exiting functionalities of the DialogSystems do not allow the dialog systems to process user requests of theend users in a manner desired by the end users.

Once a plugin is installed, the plugin may at least partially assist theDialog System Engine in interpreting and processing user requests. Inyet more embodiments, the Dialog System Engine may providerecommendations or tips to the end users to install or purchaseparticular plugins.

More specifically, once a plugin is purchased or selected by aparticular end user, the plugin may be automatically integrated with theDialog System of the end user. Further, all or certain user requests maybe processed by the installed plugin, which may ultimately extend oralter functionalities of the Dialog System of the end user in apredetermined manner. For example, default functionalities of the DialogSystem may allow searching information on the Internet, but may notallow providing fulfilment responses to user requests. In other words,the Dialog System may be not able to perform certain actions withsoftware or mobile applications, websites, and web services, such asscheduling events in a calendar application or generating emails withthe assistance of an email agent. In this example, the end user maypurchase a plugin that may extend functionalities of the Dialog Systemby allowing the Dialog System to make online reservations. The end usermay also add another plugin that may extend functionalities of theDialog System by configuring the Dialog System to interact, for example,with a navigational mobile application. In yet another example, DialogSystem functionalities can be extended by adding a plugin that canhandle user requests in a foreign language.

In further example embodiments, an end user may install an applicationfrom an application store, such as an application store associated withan operating system of a user device, e.g., Android, iOS, Windows Phone,and the like. The operating system of the user device may already have adialog system. Once the application is downloaded by the user, thedialog system of the user device may be expanded with anapplication-specific dialog system extension element.

In example embodiments, the dialog system may provide the corefunctionality (e.g., Amazon Echo) for the user device, for example, whenthe dialog system is installed together with the operating system of theuser device. In other example embodiments, the dialog system may beassociated with a dialog interface of only one application installed onthe user device.

The present technology may also allow software developers to annotatecertain functions to be performed by dialog system extension elements ina source code of software applications in a separate developmentenvironment (i.e., without the need to code dialog system functions).The annotations, when invoked, may cause downloading and installing of adialog system extension element associated with a software applicationso that a Dialog System Interface may implement desired dialog systemfunctions with respect to certain user inputs and deliver dialog systemresponses to end users. Annotations may significantly simplify thedesign process of software applications, thereby allowing the softwaredevelopers to integrate dialog system extension elements into softwareapplications without dedicating time and resources for developing andmaintaining dialog systems having embedded dialog system extensionelements.

In accordance with various embodiments of the present disclosure,software developers may insert annotations in the form of metadatawithin a source code during design time of the Dialog System.

In general, a plurality of end users may use the same Dialog System. TheDialog System may reside in a multi-user environment, for example, on aserver, so that the plurality of end users can access the Dialog system.Plugins may be enabled or bought on a per-user basis (i.e., each usermay extend the functionalities of the Dialog System by buying pluginsand associating the plugins with the Dialog System). The functionalitiesof the Dialog System provided by the plugins may be available only forthe end user who bought the plugins or installed the applicationsassociated with the plugins. Once the Dialog System receives a userrequest from the end user, the Dialog System may decide whether the userrequest is to be processed by the Dialog System itself or by any of theenabled plugins.

Plugins can generally be created and provided to the marketplace bydevelopers associated with Dialog Systems or third-party developers. Ineither case, the plugins can be provided on a free-of-charge basis orwhen purchased, thereby allowing the developers to generate profit bycooperating with the marketplace.

According to embodiments of the present disclosure, a Dialog SystemEngine may be linked with a mobile application. The mobile application,in turn, may run on a user device of an end user and may have only aDialog System Interface, while the Dialog System Engine associated withthe Dialog System Interface may reside in a network environment.Therefore, the Dialog System Engine may support the operation of theDialog System Interface. In this example, the Dialog System Interfacecan be activated by the end user when the end user interacts with themobile application. The end user can make inquiries to the Dialog SystemInterface in the form of voice inputs or text inputs. Upon receipt of auser inquiry, the Dialog System Interface can transfer the user inquirywith little or no pre-processing to the linked custom Dialog SystemEngine linked to the Dialog System Interface. The Dialog System Enginemay process the received user inquiry, interpret the user inquiry, andgenerate a response to the user inquiry based on predetermined rules andsettings. The response may be then delivered to the Dialog SystemInterface for further visual or audio presentation to the end user. Insome embodiments, the response may include a response text to bedelivered to the end user and/or metadata with instructions for the enduser device to perform (e.g., open a browser, access certain dataonline, run a particular application, etc.). In other embodiments, theresponse may include a callback Uniform Resource Identifier (URI) thatthe Dialog System Interface or user device needs to access to obtain aresponse text and/or metadata.

In general, Dialog System Interfaces can be integrated or be an integralpart of a wide range of software applications running on a clientdevice, such as a personal computer (PC) or a cellular phone, or on aserver so that the Dialog Systems become a part of a website or webservice. Dialog Systems can be implemented on a server such that theirfunctionalities can be accessible for Dialog System Interfaces over theInternet, cellular networks, or any other communications means. Anonline marketplace can also be implemented in “a cloud,” meaning it canrun on a server and be available to software developer thorough aparticular website or web interface.

Referring now to the drawings, FIG. 1 shows a high-level block diagramof example system environment 100 suitable for practicing the presenttechnologies. As shown on FIG. 1, a platform 110 for creating andmaintaining custom Dialog Systems Engines may be provided. The platform110 may include a platform interface 112 for creating custom DialogSystem Engines 120 and backend service 114 for maintaining and runningDialog System Engines 120.

The platform interface 112 may include a GUI embedded into a webpage andaccessible by developers 116 via the Internet. In some otherembodiments, however, the platform interface 112 may be implemented as asoftware application, such as a downloadable software application or anyother software, middleware, or firmware running on or accessible from anelectronic device such as a computer. In the example shown in FIG. 1,the platform interface 112 may be realized as a web accessible GUI aswill be described below. For simplicity, this disclosure describesembodiments where the platform interface 112 is a server-based solutionso that it is accessible via the Internet. Regardless of a particularimplementation, the platform interface 112 may enable the developers 116through a number of GUI tools to create one or more custom Dialog SystemEngines 120.

Still referencing to FIG. 1, the backend service 114 of the platform 110may be responsible for maintaining and running the custom Dialog SystemEngines 120 that are created, for example, by or with the help of theplatform interface 112. The backend service 114 may operate as a webservice providing functionality to custom Dialog Systems by enablingDialog System Interfaces 130 to interact with the custom Dialog SystemEngines 120 maintained at the backend service 114 of the platform 110.

As briefly discussed above, the Dialog System Interfaces 130 can beprovided on a client side 140 associated with dialog system end users118. The Dialog System Interfaces 130 may be as simple as a GUI enablingthe dialog system end users 118 to make inquiries, which may be thendelivered to the backend service 114 for processing by the correspondingDialog System Engines 120, and to receive responses to the inquiresgenerated by Dialog System Engines 120. The Dialog System Interfaces 130may be implemented as a stand-alone software application or the DialogSystem Interfaces 130 can be an integral part of a software application,mobile application, web service, website, and the like.

Still referencing to FIG. 1, the client side 140 may refer to, but isnot limited to, a user device, a terminal, a computing device (e.g., alaptop computer, a tablet computer, a desktop computer, a PC), acellular phone, a smart phone, a gaming console, a remote control, amultimedia system, a smart television device, a set-top box, aninfotainment system, an in-vehicle computing device, an informationalkiosk, a robot, and so forth. In these embodiments, the Dialog SystemInterfaces 130 may be implemented as software, middleware, or firmwareinstalled on such devices.

In additional embodiments, the client side 140 may refer to a networkedor online solution, such as a server, hosting service, web service, website, cloud service, and so forth. For example, the Dialog SystemInterface 130 can be a widget or a GUI provided on one or more web pagesenabling end users to make inquiries and get responses to the inquiries.This option may be suitable for those instances when a developer, forexample, wants to integrate a Dialog System into a website of thedeveloper to provide enhanced customer service.

As can be seen in FIG. 1, the interaction between the Dialog SystemInterfaces 130 and the corresponding Dialog System Engines 120 may beperformed via a communications network 150. The communications network150 may include one or more of the Internet, intranet, cellular network,Local Area Network (LAN), Wide Area Network (WAN), IEEE 802.11 basednetwork, and so forth.

FIG. 1 also shows various third party web resources/web services 160provided via one or more web servers. These third party webresources/web services 160 can provide information of various types tothe Dialog System Engines 120 or the Dialog System Interfaces 130 as apart of a response to a user request. For example, the web resources/webservices 160 may refer to email services, weather services, navigationservices, and the like. Accordingly, if a user makes the inquiry “Whatis the weather like today?,” such information may be automaticallyacquired by the Dialog System Engine 120 from one or more third partyweb resources/web services 160 and then integrated into a dialog systemresponse to be delivered to the dialog system end users 118.

Still referring to FIG. 1, the example system environment 100 mayinclude an online plugin marketplace, shown as a marketplace 170, formaintaining a plurality of selectable plugins. The marketplace 170 canbe implemented on a server such that it can communicate with plugindevelopers, dialog system developers, and end users. In someembodiments, however, the marketplace 170 can be integrated with theplatform 110.

The marketplace 170 may include a database 172 for storing plugins andrespective metadata. The marketplace 170 may also include a marketplaceinterface 174 for enabling the developers to review, select, purchase,and/or optionally customize selectable plugins. Metadata may accompanyeach plugin and include content associated therewith. For example, themetadata may include one or more of the following: a description ofplugins, example images, example audio messages, tags, developercomments, ranks, publisher information, payment information, statisticalinformation (e.g., a number of downloads/installs), abuse reportlinks/buttons, legal notices, hyperlinks to third party web resources,and so forth.

The marketplace interface 174 may include a GUI embedded into a webpageand accessible by the plugin developers and end users via the Internet.In some other embodiments, however, marketplace interface 174 may beimplemented as a software application, such as a downloadable softwareapplication, part of the Client Side/Dialog System Interface applicationor device or any other software, middleware, or firmware running on oraccessible from an electronic device such as a computer. In the exampleshown in FIG. 1, the marketplace interface 174 may be realized as a webaccessible GUI. For simplicity, this disclosure describes suchembodiments where the marketplace 170 is a server based solution so thatit is accessible via the Internet. Regardless of a particularimplementation, the marketplace interface 174 may enable the end users,through a number of GUI tools, to select one or more plugins andassociate them with their custom Dialog System Engines 120.

As mentioned above, plugins can be provided to end users in exchange formonetary consideration or on a free-of-charge basis. In one exampleembodiment, end users may need to make a one-time payment or subscribeto a subscription plan requiring regular payments. Accordingly, themarketplace 170 may be enabled to make financial transactions usingmonetary or non-monetary funds. For example, the marketplace 170 mayhave a credit card processing agent, an Automated Clearing House agent,and the like. Subscription plans may require payments in the amountsdependent on a number of dialog system users, period during which aplugin is used (e.g., a periodic plan such as a month-to-monthsubscription plan, yearly plan), number of plugin copies, complexity,number of functions provided by plugin, and so forth.

Some plugins may be provided on a free-of-charge basis. In one exampleembodiment, plugins can be provided free-of-charge during apredetermined period (e.g., a test period of one month), but then mayrequire a payment. In further example embodiments, plugins may beprovided to end users for trial periods. More specifically, a userrequest of the end user may be processed by a plugin by default, even ifthe end user has not subscribed, purchased, or installed the plugin. Ananswer received based on processing by the plugin may be provided to theend user. Such free providing of plugins to the end users may be donefor preview purposes or as a teaser or incentive for the end user to buythe plugin. The presentation of the response may be augmented with atext, such as “Results provided by the plugin . . . ” or the like with alink to purchase the plugin. In further embodiments, two responses maybe provided to the end user, where one response may be obtained based onprocessing of the user request by the Dialog System without the plugin,and the other response may be obtained based on processing of the userrequest by the Dialog System using the plugin. When viewing tworesponses, the end user may compare the results of processing the userrequest with and without the plugin to decide whether to purchase theplugin.

If plugins are sold from the marketplace 170, the original owner of theplugins may be compensated by the marketplace 170 from the fundscollected from the purchasers. For instance, the owners of plugins soldcan be compensated as a percentage of the funds collected at the time ofpurchase.

In order for the end users to purchase plugins through the marketplace170 and associate the purchase plugins with the Dialog Systems of theend users, the end users may be required to register with themarketplace 170 and create a user profile.

Accordingly, the marketplace 170 can be referred to a multi-user webplatform/web service allowing the end users to review, select, andpurchase plugins of their interest and integrate the plugins with DialogSystem Engines 120 used by the end users.

For illustrative purposes, the process of creating and operating customDialog System Engines 120 will now be described with reference to FIGS.1-3. In particular, the platform interface 112 may provide one or moreGUIs having a number of tools enabling developers to develop plugins inorder to create and customize one or more dialog system elements, whichserve as a basis for a Dialog System Engine 120.

According to various embodiments, dialog system elements may includeentities, intents, dialog system trees, and other dialog system data andmetadata. Each entity may refer to a number of objects having the sameor similar characteristics. In other words, entities may include listsof terms and/or keywords defining objects of one class. In one exampleembodiment, an entity may refer to a keyword and a set of synonyms ofthe keyword. In another example embodiment, an entity may refer to akeyword and a set of its definitions. In yet another example embodiment,an entity may refer to a list (e.g., a list of cities, list of names,list of titles, list of brands, list of street names, etc.).

In some embodiments, each entity can have a title. For example, oneentity can be titled as “city” and may contain a list of cities such asAlexandria, Arlington, Boston, and so forth. In other embodiments, anentity can be titled as a keyword and can contain synonyms and/ordefinitions of this keyword. In one example embodiment, the entitycalled “music” may include the terms of song, singer, singing, musician,and so forth. In another example embodiment, the entity called “artist”may include a list of music bands, music ensembles, or music artists. Inanother example embodiment, the entity called “Beatles” may include alist of possible synonyms, such as “The Beatles,” “Beatles,” “Fab Four,”“Liverpool Legends,” “John Lennon,” and so forth. In yet another exampleembodiment, there can be an entity called “Artist” which may includevarious artist names, artist name synonyms, music band names, and soforth.

In some embodiments, the Dialog System Engines may include a number ofdefault, pre-configured entities and/or intents. These can includecommon types of entities or intents related to such concepts as time,date, location, etc. For example, when a developer creates a new DialogSystem Engine, it may already have a few entities of common type such as“@System.Date” entity. This entity may cover linguistically constructsrelated to particular dates and may include the following terms:“today,” “tomorrow,” “next week,” “January 1,” “January 1 of next year,”“next Monday,” “the following Monday,” and so forth.

Further, each intent of a Dialog System Rule may include a dialog systeminteraction scheme, which may provide a particular relation between atleast one user request and at least one dialog system linguisticresponse or fulfilment response. The dialog system interaction schemecan be represented by a rule based on a relationship between aparticular action and at least one entity. Actions generally relate toformalized software objects such as JSON (JavaScript Object Notation)objects causing at least one processor to generate linguistic orfulfilment responses associated with at least one entity. Accordingly,each intent can be represented as a logical relation between at leastone action and at least one entity object, for example, as follows:

-   -   a) [Action] @[Entity]    -   b) [Action] @[Entities]    -   c) [Actions] @[Entity]    -   d) [Actions] @[Entities]    -   e) Text @[Entity]    -   f) Text @[Entities]    -   g) Text @[Entity] Text    -   h) [Action] Text @[Entity]

The procedures a) through d) mean that a particular Action or severalActions shall be performed by client side 140 and/or Dialog SystemInterface 130 with respect to a predetermined Entity or severalEntities. For example, one intent may be represented as “Play @Artist,”where @Artist is a developer-defined entity containing a set of artists.In this example, the intent orders the Custom Dialog System Engine 120to activate the playback of at least one Beatles song, depending on acontext.

The procedures e) through h) mean that particular information in theform of text is provided with respect to a particular Entity. Forexample, the user request “Create a meeting with John at 1 p.m.tomorrow, please” may be presented as the following pattern: [Action]Text @[sys.date-time] Text. Here, @[sys.date-time] refers to an entityassociated with time and date, while the phrase “Create a meeting”refers to a predetermined action to be performed by Dialog SystemInterface 130 or Custom Dialog System Engine 120 with a certain mobileapplication, software application, or web service. Element “Text” refersto content and not entity nor intent.

Intents can also have fulfilment capabilities to generate response text,call external services, and the like. Intents can also have childintents to allow simpler definition of dialog trees. Additionally,actions may be used to define what needs to be collected in a dialogsession (when the end user provides a user request and the dialog systemprovides a response to the user request).

As mentioned above, a dialog system rule may cause generation of alinguistic response and/or fulfilment response as an answer to a userrequest. One example of a linguistic response may include particularizedcontent deliverable as an audio message or displayable message.Fulfilment responses may refer to particular processor-executableinstructions for one or more software applications, middleware,firmware, web service, and the like that cause implementation of aparticular action. Some examples of fulfilment responses may includescheduling an event in a calendar mobile application, writing andsending a text message or email, searching for content at a web searchservice, building a route in a navigational software application, and soforth. In certain embodiments, at least some linguistic responses and/orfulfilment responses can be configured by developers. In otherembodiments, at least some linguistic responses and/or fulfilmentresponses can be pre-configured and be available as default responses.

In certain additional embodiments, developers can provide not entitiesand intents but just example requests to illustrate intents andentities. In these embodiments, the platform 110 may automaticallydetermine, using machine-learning techniques, what entities and intentsare implied in example user requests and create corresponding rules. Forexample, a developer may simply provide example requests, such as “PlayBeatles” and “I'd like to listen to Madonna,” and the platform 110 maymatch “Beatles” and “Madonna” to existing entities (system's or user's)and generate corresponding “[Action] @[Entity]” rules automatically.

Thus, developers can use the platform interface 112 to generate aplurality of dialog system rules specific to a particular application orindustry. These pluralities of entities and intents form dialog systemrules (also referred to as dialog system elements) and enable the customDialog System Engines to perform certain actions or generate certainoutputs in response to a wide range of end user inputs.

FIG. 2 is a process flow diagram showing a method 200 for creatingcustom Dialog System Engines using a platform shown as the platform 110on FIG. 1 and for operating the platform according to an exampleembodiment. The method 200 may be performed by processing logic that maycomprise hardware (e.g., decision-making logic, dedicated logic,programmable logic, and microcode), software (such as software run on ageneral-purpose computer system or a dedicated machine), or acombination of both. In one example embodiment, the processing logicrefers to one or more components of the platform. Notably, the belowrecited steps of the method 200 may be implemented in an order differentthan described and shown in FIG. 2. Moreover, the method 200 may haveadditional steps not shown herein, but which can be evident for thoseskilled in the art from the present disclosure. The method 200 may alsohave fewer steps than outlined below and shown in FIG. 2.

At operation 205, an application developer may be enabled to registerwith the platform. To these ends, the developer may need to interactwith a platform interface. The registration may include creating adeveloper profile, which can be maintained by the platform. Thedeveloper profile may link (i.e., associate) a custom Dialog SystemEngine of this developer and one or more Dialog System Interfacesdeployed on a client side. The linking may include stipulatingApplication Programming Codes, rules for interaction, destinationaddresses, and so forth.

At operation 210, the platform may receive from the developer one ormore entities and store the received entities at a local database. Insome embodiments, the entities may be not received, but created by thedeveloper using web tools of the platform interface.

At operation 215, the platform may receive from the developer one ormore intents and store the intents at the local database. In someembodiments, the intents may be not received, but created by thedeveloper using tools of the platform interface. As described above, theintents may be associated with the entities, and intents and entitiestogether may form dialog system elements (custom rules enabling theDialog System Engine to generate responses tailored for specific needs).

At operation 220, the platform may associate one or more entities withone or more intents to create (i.e., form) the custom Dialog SystemEngine. The custom Dialog System Engine may be associated with one ormore Dialog System Interfaces of the developer.

Operations 205-220 illustrate a set-up process for the custom DialogSystem Engine, while the following operations 225-245 illustrate theoperation of a custom Dialog System Engine. Once all dialog systemelements of custom Dialog System Engine are created, the dialog systemelements may be maintained as a backend service and enable any of theassociated Dialog System Interfaces to provide the full functionality ofthe Dialog System to users according to predetermined settings.

At operation 225, the platform may receive a user request from anunidentified Dialog System Interface. The user request can be a voiceinput or text input. In some embodiments, the Dialog System Interfacecan pre-process the user input, for example, by recognizing spoken wordsand transforming the voice input into text input. In other embodiments,however, no pre-processing is performed by Dialog System Interface 130.

At operation 230, the platform may process the user request and identifythe Dialog System Interface and the Dialog System Engine associated withthe identified Dialog System Interface. In particular, the user requestcan be accompanied by an identifier when the user request is sent fromthe Dialog System Interface to the platform.

At operation 235, based on the result of the identification at operation230, the platform may activate the custom Dialog System Engineassociated with the identified Dialog System Interface. At the sameoperation, the platform may also retrieve or identify one or more dialogsystem elements (such as one or more entities, one or more intents, oneor more keywords, synonyms of the keywords, definitions of the keywords,reference values, dialog system trees, lists of terms, and the like)based on the result of the identification at operation.

At operation 240, the Dialog System Engine may select the appropriatedialog system elements and process the user request using identifieddialog system elements (such as one or more entities, one or moreintents, one or more keywords, synonyms of the keywords, definitions ofthe keywords, reference values, dialog system trees, lists of terms, andthe like) as retrieved at operation 235.

At operation 245, the Dialog System Engine may generate a response andsend the response to the Dialog System Interface associated with thecustom Dialog System Engine 120. The Dialog System Interface may thendisplay and/or playback the response to the end user depending onpredetermined settings.

FIG. 3 shows a high-level architecture of exemplary Dialog System Engine300, according to an example embodiment. It should be noted that eachmodule of the Dialog System Engine 300 or associated architectureincludes hardware components, software components, or a combinationthereof. The Dialog System Engine 300 may be embedded or installed in auser device or server, or may be presented as a cloud computing moduleand/or a distributed computing module.

In the embodiment shown, the Dialog System Engine 300 may include anAutomatic Speech Recognizer (ASR) 310 configured to receive and processa speech-based user input 305 into a sequence of parameter vectors. TheASR 310 may further convert the sequence of parameter vectors into arecognized input (i.e., a textual input having one or more words,phrases, or sentences). The ASR 310 may include one or more speechrecognizers, such as a pattern-based speech recognizer, free-dictationrecognizer, address book based recognizer, dynamically createdrecognizer, and so forth.

Further, the Dialog System Engine 300 may include an NLP module 320 forunderstanding spoken language input. Specifically, the NLP module 320may disassemble and parse the recognized input to produce utterances,which are then analyzed utilizing, for example, morphological analysis,part-of-speech tagging, shallow parsing, and the like. The NLP module320 may then map recognized input or its parts to meaningrepresentations.

The Dialog System Engine 300 may further include a dialog manager 330,which may coordinate the activity of all components, controls dialogflows, and communicates with external applications, devices, services,or resources. The dialog manager 330 may play many roles, which includediscourse analysis, knowledge database query, and system actionprediction based on the discourse context. In some embodiments, thedialog manager 330 may contact one or more task managers (not shown)that may have knowledge of specific task domains. In some embodiments,the dialog manager 330 may communicate with various computational orstorage resources 340, which may include, for example, a contentstorage, rules database, recommendation database, push notificationdatabase, electronic address book, email or text agents, dialog historydatabase, disparate knowledge databases, map database, points ofinterest database, geographical location determiner, clock, wirelessnetwork detector, search engines, social networking websites, bloggingwebsites, news feeds services, and many more. In some embodiments,computational or storage resources 340 may include one or more webresources/web services 160 as shown on FIG. 1 and discussed above.

Referring back to FIG. 3, the dialog manager 330 may employ multipledisparate approaches to generate an output in response to recognizedinputs. Some approaches include using statistical analysis,machine-learning algorithms (e.g., neural networks), heuristic analysis,and so forth. The dialog manager 330 may be one of the centralcomponents of the Dialog System Engine. The major role of the dialogmanager 330 may be to select the correct system actions based onobserved evidences and inferred dialog states from the results of theNLP (e.g., dialog act, user goal, and discourse history). In addition,the dialog manager 330 may be able to handle errors when the user inputhas ASR and NLP errors caused by noises or unexpected inputs.

The Dialog System Engine 300 may further include output renderer 350 fortransforming the output 360 of dialog manager 330 into a form suitablefor providing to the user. For example, the output renderer 350 mayemploy a text-to-speech engine or may contact a pre-recorded audiodatabase to generate an audio message corresponding to the output 360 ofthe dialog manager 330. In certain embodiments, the output renderer 350may present or cause to present the output 360 of the dialog manager 330as a text message, an image, or a video message for further displayingon a display screen of the user device. In some example embodiments, theoutput renderer 350 can constitute at least a part of the Dialog SystemInterface shown as the Dialog System Interface 130 on FIG. 1.

Still referring to FIG. 3, the Dialog System Engine 300 may include oneor more dialog system rules maintained in at least one rule database360. The Dialog System Engine 300 may also include or be associated withone or more context databases 370, which may maintain a plurality ofcontext description elements, such as lists of terms, keywords, phrases,expressions, context variables, and context parameters (e.g.,geolocation, system rate, GUI, etc.) associated with one or more dialogsystem rules. In other words, the context databases 370 may includeinformation supporting the process of determining conversational orenvironmental context for particular user requests.

The Dialog System Engine 300 may also include or be associated with oneor more statistics and usage databases 380, which may be configured toaggregate statistical or usage information associated with the operationof the Dialog System Engine 300 and/or associated the Dialog SystemInterface and/or associated mobile or software application. For example,statistics and usage database 380 may accumulate dialog system logs,which can be later used for optimization of dialog system rules, dialogsystem responding schemes, training machine-learning algorithms ifemployed by Dialog System Engine, and so forth.

FIG. 4-6 illustrate various screenshots of a platform interface, whichshow the process of manually creating entities (see FIG. 4) and manuallycreating intents (see FIGS. 5 and 6) by developers.

FIG. 4 shows an example GUI 400 of a platform interface for creating anew dialog system entity as discussed above. When the developer desiresto create a custom dialog system engine, the developer may define dialogsystem entities and intents using web tools of the platform interface,such as the GUI 400. Using the GUI 400, the developer can enterreference value 410 (or a canonical value for a given entity value) fora keyword and enter a synonym 420 or a list of synonyms 420 for theprovided reference value 410 in the corresponding fields provided by GUI400. The dialog system entities may include a keyword (or referencevalue) and synonyms to the keyword, a keyword and definitions of thekeyword, a list of keywords defining objects of one class, and so forth.Keywords or reference values with their synonyms and/or definitions maycompose a dialog system entity.

FIG. 5 shows an example GUI 500 of a platform interface for creating anew dialog system intent as discussed above. The dialog system intentmay define a relation between a user request and a dialog systemresponse and may be associated with a rule based on a relationshipbetween a particular action and an entity. In general, each intent canbe represented as the following computer-readable procedure “[Action]@[Entity]” or “[Action] @[Entities].” Using GUI 500, the developer mayadd user expressions 502 (e.g. “Weather @city”) to illustrate intentsand entities. Each expression may have an alias (i.e., a variable name).Based on the user expressions 502, the platform may automaticallydetermine, using machine-learning techniques, what entities and intentsare implied in example requests and create a corresponding rule. Forexample, the developer may simply provide example requests, such as“Weather forecast for Los Angeles.” The platform may match “Los Angeles”to existing entities (system or user defined) and generate corresponding“[Action]@[Entity]” rules automatically. Additionally or alternatively,the developer may provide an example request where one or more entitiesare presented explicitly, such as “What is the weather in@say.geo-city:geo-city-us.” In example of FIG. 5, “weather” andparameters associated with action 504 (aliases may be referenced inactions) are “geo-city-us” and “geo-city.” The developer can furthermodify the action 504 and provide a fulfilment 506 for the action 504.Aliases may also be references in a speech string of the fulfilment 506.

The created rule may mean that a particular action needs to be performedby a client side with respect to the entity or several entities. Forexample, one intent may be represented as “looking up forecast for$geo-city-us.” In this example, the intent may order the dialog systemengine to look for the forecast in Los Angeles.

FIG. 6 shows an example GUI 600 of a platform interface for creating anew dialog system intent. FIG. 6 shows that result 602 of execution ofprocessing the user request may be shown to the developer in a testconsole. Additionally, a reference value 604 that passed as a parametermay be shown.

FIG. 7 is a high-level block diagram illustrating an example system 700for enhancing functionalities of dialog systems described herein. Inparticular, the system 700 may be a server-based solution suitable forrunning a platform 110 and/or a marketplace 170 shown on FIG. 1.

Note that all components of the system 700 shown on FIG. 7 may includelogic elements, hardware components, software (firmware) components,virtual components, or a combination thereof. The system 700 mayinclude, relate, or constitute an integral part of one or more of avariety of types of devices and systems such as a general-purposecomputer, server, web server, network service, cloud-computing service,and so forth. Further, all modules shown in FIG. 7 may be operativelycoupled using any suitable wired, wireless, radio, electrical, oroptical standards.

As shown in FIG. 7, the system 700 includes the following hardwarecomponents: at least one processor 702, a memory 704, optionally one ormore storage devices 706, and optionally a network interface 708. Thesystem 700 may also optionally include the following software or virtualcomponents: an operating system 710, one or more software applications720, and an interface 730 (such as a platform interface 112 and/ormarketplace interface 174 shown on FIG. 1). The interface 730 mayprovide a human-centric interface for accessing and managing informationas discussed herein.

In some embodiments, the processor 702 may be configured to implementfunctionality and/or process instructions for execution within thesystem 700. For example, the processor 702 may process instructionsstored in the memory 704 and/or instructions stored on the storagedevices 706. Such instructions may include components of the operatingsystem 710, the software applications 720, and/or the interface 730.

The memory 704, according to one example embodiment, may be configuredto store information within system 700 during operation. The memory 704,in some example embodiments, may refer to a non-transitorycomputer-readable storage medium or a computer-readable storage device.In some example embodiments, the memory 704 may be a temporary memory,meaning that a primary purpose of the memory 704 may not be long-termstorage. The memory 704 may also refer to a volatile memory, meaningthat the memory 704 may not maintain stored contents when the memory 704is not receiving power. Examples of volatile memories include randomaccess memories (RAM), dynamic random access memories (DRAM), staticrandom access memories (SRAM), and other forms of volatile memoriesknown in the art. In some examples, the memory 704 may be used to storeprogram instructions for execution by the processor 702. The memory 704,in one example embodiment, may be used to temporarily store informationduring program execution.

One or more storage devices 706 can also include one or more transitoryor non-transitory computer-readable storage media and/orcomputer-readable storage devices. In some embodiments, the storagedevices 706 may be configured to store greater amounts of informationthan the memory 704. The storage devices 706 may further be configuredfor long-term storage of information. In some examples, the storagedevices 706 include non-volatile storage elements. Examples of suchnon-volatile storage elements include magnetic hard discs, opticaldiscs, solid-state discs, flash memories, forms of electricallyprogrammable memories (EPROM) or electrically erasable and programmablememories (EEPROM), and other forms of non-volatile memories known in theart. In one example, the storage devices 706 can include a databaseshown as a database 172 on FIG. 1 (i.e., the storage devices 706 canstore and maintain multiple dialog system extension elements, whichinclude plugins, add-ons, extensions, etc.). In other embodiments, thestorage devices 706 can store and maintain user profiles and customDialog System Engines.

Still referencing to FIG. 7, the system 700 may include a networkinterface 708. The network interface 708 can be utilized to communicatewith external devices, servers, and networked systems via one or morecommunications networks such as one or more wired, wireless, or opticalnetworks including, for example, the Internet, intranet, LAN, WAN,cellular phone networks (e.g. Global System for Mobile (GSM)communications network, packet switching communications network, circuitswitching communications network), Bluetooth radio, and an IEEE802.11-based radio frequency network, among others. The networkinterface 708 may be a network interface card, such as an Ethernet card,optical transceiver, radio frequency transceiver, or any other type ofdevice that can send and receive information. Other examples of suchnetwork interfaces may include Bluetooth®, 3G, 4G, and WiFi® radios inmobile computing devices as well as a Universal Serial Bus.

The operating system 710 may control one or more functionalities ofsystem 700 or components of the system 700. For example, the operatingsystem 710 may interact with the interface 730, and may furtherfacilitate one or more interactions between the software applications720 and processor 702, memory 704, storage devices 706, and/or networkinterface 708. The operating system 710 may interact with or beotherwise coupled to the interface 730 and components of the interface730. Notably, the system 700 and its components may also interact withone or more remote storage or computing resources including, forexample, web resources, web sites, social networking websites, bloggingwebsites, news feeds, email servers, web calendars, event databases,ticket aggregators, map databases, points of interest databases, and soforth. Software applications 720, in essence, may provide functionalityto the platform and/or the marketplace and enable their operation.Alternatively, the software applications 720 may be additions to theplatform and/or the marketplace.

FIG. 8 is a process flow diagram showing a method 800 for enhancingfunctionalities of dialog systems according to an example embodiment.The method 800 may be performed by processing logic that may comprisehardware (e.g., decision-making logic, dedicated logic, programmablelogic, and microcode), software (such as software run on ageneral-purpose computer system or a dedicated machine), or acombination of both. In one example embodiment, the processing logicrefers to one or more components of marketplace 170 and/or the platform110 shown on FIG. 1. Notably, the below recited steps of method 800 maybe implemented in an order different than described and shown in FIG. 8.Moreover, the method 800 may have additional steps not shown herein, butwhich can be evident for those skilled in the art from the presentdisclosure. The method 800 may also have fewer steps than outlined belowand shown in FIG. 8.

The method 800 may commence at operation 810 with maintaining an onlinemarketplace. The online marketplace may be maintained by a memory andmay include a plurality of dialog system extension elements (e.g., adialog system plugin, a dialog system add-on, a dialog system update, adialog system upgrade, and so forth). End users may view and select(purchase) particular dialog system extension elements through amarketplace interface. The marketplace interface can be available to endusers at a website or mobile application associated with a Dialog System(i.e., may be implemented as a dialog system interface). The end userscan review metadata associated with dialog system extension elementsthrough the marketplace interface, and comments, ranks, ratings,reviews, publisher's information, description, manuals, images, videos,legal information, and so forth. In some embodiments, the end users maynot need to visit the marketplace interface, but may only need tocommunicate with the Dialog System to learn about certain dialog systemextension elements. In yet more embodiments, the Dialog System maymonitor interaction between the end user and the dialog system.Furthermore, based on the monitoring, the Dialog System may providerecommendations to the end users to install particular dialog systemextension elements in view of historical data of interaction between theend user and the Dialog System associated with the end user. Theinstalling may mean associating the dialog system extension elementswith the Dialog System. For example, the end user may request that theDialog System to provide a particular response. However, existingfunctionalities of the Dialog System may not allow the Dialog System toprocess the user request in a manner desired by the end user. In thiscase, the Dialog System may suggest to the end user that the userrequest cannot be addressed at this time, unless the end user purchasesan additional plugin that is specifically designed to handle such typeof user requests. The end user may follow the suggestion of the DialogSystem and make a purchase.

More specifically, at operation 820, a processor may receive selectionof at least one of the plurality of dialog system extension elementsfrom the end user. The end user may be associated with the DialogSystem. In other words, the end user may have a dialog system interfaceinstalled on a user device of the end user. Therefore, the selection ofthe dialog system extension element may be received from the dialogsystem interface. The dialog system interface may be associated with thedialog system that may be maintained in a network environment (e.g., ona server associated with the online platform). In further exampleembodiments, the dialog system may be maintained at the user device. Theselection of the dialog system extension element may be made by the enduser based on one or more of the following: a dialog state, userpreferences, dialog system heuristics, a connectivity state, a dialogsystem state, ranking of each of the plurality of dialog systemextension elements in the online marketplace, settings set by the enduser, weights assigned to each of the plurality of dialog systemextension elements, a type of user request supported by the one of theplurality of dialog system extension elements, and so forth.

In some example embodiments, the selection of the dialog systemextension element may include activating one or more annotations. Theannotations may be embedded into a software application installed on auser device. More specifically, the annotations may include a codewithin the software application. The annotations may be associated withthe dialog system extension element. When the annotations are activated,i.e. when the code associated with the annotations is invoked, theassociating of the dialog system extension elements with the dialogsystem may be initiated.

In a further example embodiment, the dialog system extension elementsmay be identified automatically by the Dialog System based on softwareapplications installed on the user device or on the online platform, orbased on other factors, such as a status of the user device, ageographical location of the user device, such as a Global PositioningSystem data associated with the user device, and other personal andcontextual information concerning the user and the user device.

In a further example embodiment, the dialog system may be associatedwith a virtual assistant. The virtual assistant may be at leastpartially installed on a user device associated with the end user (i.e.,the virtual assistant may be installed either on the user device or onthe online platform, while a GUI associated with the virtual assistantmay be running on the user device for both types of installation of thevirtual assistant).

In some embodiments, the selection may require making a financialtransaction so that the plugin can be integrated with a particularDialog System Engine associated with the end user. In these cases, theend user may need to subscribe to a subscription plan or make a lump sumpayment for the right to use the selected plugin. More specifically,upon receiving the selection of the dialog system extension element, theprocessor may receive, from the end user, the selection of thesubscription plan associated with the dialog system extension element.Furthermore, the processor may receive a payment for the dialog systemextension element. The payment may be provided by the end user inaccordance with the subscription plan.

At operation 830, the processor may associate the dialog systemextension element selected (and purchased) by the end user with theDialog System. In particular, the processor may need to identify the enduser and/or the Dialog System associated with the end user. Theauthorization can be accomplished by an authorization process (i.e.,requesting that the end user login to the marketplace). Morespecifically, the processor may receive an authorization request fromthe end user. The authorization request may include at leastauthorization data associated with the end user. Based on theauthorization data, the processor may communicate with the platform andaccess the records associated with the end user and the dialog system,such as records associated with a user profile of the end user, with therecords being stored in the memory. Based on the records, the end userand the dialog system associated with the end user may be identified.Based on the identification, the processor may authorize an access ofthe end user to the online marketplace. Once the end user and/or theDialog System is/are identified, the processor may proceed to linkingthe Dialog System with the dialog system extension element selected bythe end user. In an example embodiment, the linking process may meanthat the dialog system extension element is integrated or embedded intothe Dialog System or, alternatively, certain links or metadata areintegrated with the Dialog System. In a further example embodiment, eachof the plurality of dialog system extension elements may be associatedwith metadata, which may be provided for a review to the end user. Inthis embodiment, the association of the dialog system extension elementwith the dialog system may include integrating the metadata associatedwith the dialog system extension element into the dialog system. Ineither case, the dialog system extension element may operate inconjunction with the Dialog System.

Further, when the dialog system extension element is successfullyassociated with the Dialog System, the operation of the Dialog Systemcan be as follows. At operation 840, the processor may receive a userrequest of a user from a Dialog System Interface. In exampleembodiments, the dialog system interface may be installed on a userdevice or a third party server. The dialog system interface mayassociate with the dialog system maintained at the online platform. Atoperation 850, the processor may identify the Dialog System Engineassociated with Dialog System Interface and/or the end user. Atoperation 860, the processor may identify the dialog system extensionelement or several dialog system extension elements, which areassociated with the Dialog System Engine and are associated with userpreferences that match the user request. At operation 870, the userrequest may be processed by the dialog system extension element alone orin conjunction with the Dialog System to generate a response or afulfilment action to the user request. In some embodiments, the DialogSystem Engine may attempt to process the user request without any dialogsystem extension elements. More specifically, during the processing, thedialog system may be activated and one or more dialog system entities,one or more dialog system intents, one or more keywords, synonyms of thekeywords, definitions of the keywords, reference values, dialog systemtrees, lists of terms, and the like may be retrieved. The user requestmay be processed by applying the one or more dialog system entities andthe one or more dialog system intents to generate the response. If theprocessing of the user request by the dialog system (without the dialogsystem extension element) is successful, the response is delivered tothe user at operation 880 via the Dialog System Interface. If processingof the user request by the dialog system alone is unsuccessful, the userrequest may be processed using the dialog system extension elements togenerate a substitute response to the user request. The substituteresponse may be delivered to the user. The delivering of the response orthe substitute response may include delivering, to the Dialog SystemInterface or the user device, text, video, audio, and/or metadata, suchas a callback URI where the user device can obtain data for deliveringto the end user.

In another example embodiment, the Dialog System Engine may process theuser request with a dialog system extension element. More specifically,the processor may receive the user request from the dialog systeminterface. Based on the user request, the processor may identify thatthe dialog system interface is associated with the dialog system. Theprocessor may further identify at least one dialog system extensionelement that is associated with the dialog system and applicable forprocessing the user request. The processor may process the user requestusing the dialog system extension element to generate a response to theuser request. The response may be delivered to the user.

In another example embodiment, the Dialog System Engine may provideresponses obtained with and without the dialog system extension elementto the end user. More specifically, the processor may receive the userrequest from the dialog system interface. The processor may identifythat the dialog system interface is associated with the dialog system.Based on the user request, the processor may activate the dialog systemand process the user request using the dialog system to generate a firstresponse. Furthermore, the processor may identify at least one dialogsystem extension element on the online marketplace that may beapplicable for processing the user request. The processor may furtherprocess the user request using the dialog system extension element togenerate a second response to the user request. The processor mayfurther cause delivery of the first response and the second response tothe end user. The second response may be accompanied with an incentivefor the end user to buy the dialog system extension element by which theuser request was processed.

FIG. 9 is a high-level block diagram illustrating an example user device900 suitable for implementing the methods described herein. It is worthmentioning that all components of the user device 900 may include logicelements, hardware components, software (firmware) components, virtualcomponents, or a combination thereof.

The user device 900 may include at least an integral part of one or moreof a variety of types of devices and systems such as a general-purposecomputer, desktop computer, server, computer network, network service,cloud-computing service, and so forth. Further, all modules shown inFIG. 9 may be operatively coupled using any suitable wired, wireless,radio, electrical, or optical standards. As already outlined above, theuser device 900 may refer to a smart phone, wireless telephone,computer, such as a tablet computer or desktop computer, infotainmentsystem, in-vehicle computing device, and the like.

As shown in FIG. 9, the user device 900 may include the followinghardware components: at least one processor 902, a memory 904, one ormore storage devices 906, one or more input modules 908, one or moreoutput modules 910, a network interface 912, and a geo locationdeterminer 914. The user device 900 may also include the followingsoftware or virtual components: an operating system 920, one or moresoftware (mobile) applications 930, and a dialog system interface 130,which can be a stand-alone software application or be integrated intoone or more software applications 930. The dialog system interface 130may provide a human-centric interface for accessing and managinginformation as discussed herein, communicating with a dialog systemengine, and communicating with web resources/web services. According tovarious embodiments, the dialog system interface 130 can be virtual.

The processor 902 may be configured to implement functionality and/orprocess instructions for execution within the user device 900. Forexample, the processor 902 may process instructions stored in the memory904 and/or instructions stored on the storage devices 906. Suchinstructions may include components of the operating system 920 and thesoftware applications 930. The user device 900 may also include one ormore additional components not shown in FIG. 9, such as a housing, powersupply, communication bus, and the like. These elements are omitted soas to not burden the description of present embodiments.

The memory 904, according to one example embodiment, may be configuredto store information within the user device 900 during operation. Thememory 904 may refer to a non-transitory computer-readable storagemedium or a computer-readable storage device. In some examples, thememory 904 may be a temporary memory, meaning that a primary purpose ofthe memory 904 may not be long-term storage. The memory 904 may alsorefer to a volatile memory, meaning that the memory 904 may not maintainstored contents when the memory 904 is not receiving power. Examples ofvolatile memories include RAM, DRAM, SRAM, and other forms of volatilememories known in the art. In some examples, the memory 904 may be usedto store program instructions for execution by the processor 902. Thememory 904, in one example embodiment, may be used by software (e.g.,the operating system 920) or the dialog system interface 130 executingon the user device 900 to temporarily store information during programexecution. The storage devices 906 can also include one or moretransitory or non-transitory computer-readable storage media and/orcomputer-readable storage devices. In some embodiments, the storagedevices 906 may be configured to store greater amounts of informationthan the memory 904. The storage devices 906 may further be configuredfor long-term storage of information. In some examples, the storagedevices 906 may include non-volatile storage elements. Examples of suchnon-volatile storage elements include magnetic hard discs, opticaldiscs, solid-state discs, flash memories, forms of EPROM or EEPROM, andother forms of non-volatile memories known in the art.

Still referencing to FIG. 9, the user device 900 may include one or moreinput modules 908. The input modules 908 may be configured to receiveuser inputs. Examples of the input modules 908 may include a microphone,keyboard, keypad, mouse, trackball, touchscreen, touchpad, or any otherdevice capable of detecting an input from a user or other source in theform of speech, audio, or tactile actions, and relaying the input to theuser device 900 or components thereof.

The output modules 910, in some example embodiments, may be configuredto provide output to users through visual or auditory channels. Theoutput modules 910 may include a video graphics adapter card, liquidcrystal display monitor, light emitting diode monitor, sound card,speaker, or any other device capable of generating output that may beintelligible to a user.

The user device 900, in some embodiments, may include the networkinterface 912. The network interface 912 can be utilized to communicatewith external devices, servers, and networked systems via one or morecommunications networks such as one or more wired, wireless, or opticalnetworks including, for example, the Internet, intranet, LAN, WAN,cellular phone networks (e.g. GSM communications network, packetswitching communications network, circuit switching communicationsnetwork), Bluetooth radio, and an IEEE 802.11-based radio frequencynetwork, among others. The network interface 912 may be a networkinterface card, such as an Ethernet card, optical transceiver, radiofrequency transceiver, or any other type of device that can send andreceive information. Other examples of such network interfaces mayinclude Bluetooth®, 3G, 4G, and WiFi® radios in mobile computing devicesas well as a Universal Serial Bus.

The user device 900 may further include the geo location determiner 914for determining a current geographical location of the user device. Thegeo location determiner 914 may utilize a number of different methodsfor determining geographical location including, for example, receivingand processing signals of Global Positioning Systems, GLONASS satellitenavigation systems, or the Galileo satellite navigation system;utilizing multilateration of radio signals between radio towers (basestations); or utilizing geolocation methods associated with InternetProtocol addresses, Media Access Control addresses, Radio-FrequencyIdentification, or other technologies.

The operating system 920 may control one or more functionalities of theuser device 900 or its components. For example, the operating system 920may interact with the dialog system interface 130 and may furtherfacilitate one or more interactions between the software applications930 and one or more of the processor 902, the memory 904, the storagedevices 906, the input modules 908, and the output modules 910. As shownin FIG. 9, the operating system 920 may interact with or be otherwisecoupled to the software applications 930, the dialog system interface130, and components thereof. In some embodiments, the dialog systeminterface 130 can be included into the operating system 920 and/or thesoftware applications 930. Notably, the user device 900 and itscomponents, such as the dialog system interface 130, may also interactwith one or more remote storage or computing resources including, forexample, web resources, websites, social networking websites, bloggingwebsites, news feeds, email servers, web calendars, event databases,ticket aggregators, map databases, points of interest databases, and soforth.

Thus, methods and systems for enhancing functionalities of dialogsystems by end users have been described. Although embodiments have beendescribed with reference to specific example embodiments, it will beevident that various modifications and changes can be made to theseexample embodiments without departing from the broader spirit and scopeof the present application. Accordingly, the specification and drawingsare to be regarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A system for enhancing functionalities of dialogsystems, comprising: a memory operable to maintain an online marketplacecomprising a plurality of dialog system extension elements, wherein eachof the plurality of dialog system extension elements includes at leastone of a dialog system plugin, a dialog system add-on, a dialog systemupdate, and a dialog system upgrade; and at least one processor operableto: receive a selection of one of the plurality of dialog systemextension elements from an end user, the end user being associated witha dialog system; and based on the selection, associate the one of theplurality of dialog system extension elements with the dialog systemassociated with the end user.
 2. The system of claim 1, wherein the atleast one processor is further operable to: monitor interaction betweenthe end user and the dialog system; and based on the monitoring, providea recommendation to the end user to install the at least one of theplurality dialog system extension elements, the installing including theassociation of the one of the plurality of dialog system extensionelements with the dialog system.
 3. The system of claim 1, wherein thedialog system is associated with a virtual assistant, the virtualassistant being at least partially installed on a user device associatedwith the end user.
 4. The system of claim 1, wherein the selection ofthe one of the plurality of dialog system extension elements is made bythe end user based on one or more of the following: a dialog state, userpreferences, dialog system heuristics, a connectivity state, a dialogsystem state, ranking of each of the plurality of dialog systemextension elements in the online marketplace, settings set by the enduser, weights assigned to each of the plurality of dialog systemextension elements, and a type of user request supported by the one ofthe plurality of dialog system extension elements.
 5. The system ofclaim 1, wherein the selection of the one of the plurality of dialogsystem extension elements is received from a dialog system interface,wherein the dialog system interface is installed on a user deviceassociated with the end user, the dialog system interface beingassociated with the dialog system maintained at one or more of the userdevice and an online platform.
 6. The system of claim 1, wherein the atleast one processor is further operable to: receive an authorizationrequest from the end user, the authorization request including at leastauthorization data associated with the end user; based on theauthorization data, access records associated with the end user and thedialog system associated with the end user, the records being stored inthe memory; based on the records, identify the end user and the dialogsystem associated with the end user; and based on the identifying,authorize an access of the end user to the online marketplace.
 7. Thesystem of claim 1, wherein the associating of the one of the pluralityof dialog system extension elements with the dialog system includesembedding the one of the plurality of dialog system extension elementsinto the dialog system.
 8. The system of claim 1, wherein each of theplurality of dialog system extension elements is associated withmetadata, the metadata being provided to the end user for a review. 9.The system of claim 8, wherein the associating of the one of theplurality of dialog system extension elements with the dialog systemincludes integrating the metadata associated with the one of theplurality of dialog system extension elements into the dialog system.10. The system of claim 1, wherein the at least one processor is furtheroperable to: receive a user request of the end user from a dialog systeminterface, wherein the dialog system interface is installed on one of auser device and a third party server, the dialog system interface beingassociated with the dialog system, wherein the dialog system ismaintained at an online platform; based on the user request, activatethe dialog system and retrieve at least one or more dialog systementities and one or more dialog system intents; process the user requestby applying the one or more dialog system entities and the one or moredialog system intents to generate a response; if the processing of theuser request is successful, deliver the response to the end user; and ifthe processing of the user request is unsuccessful, process the userrequest by the one of the plurality of dialog system extension elementsto generate a substitute response to the user request and deliver thesubstitute response to the end user.
 11. The system of claim 1, whereinthe at least one processor is further operable to: receive a userrequest of the end user from a dialog system interface, wherein thedialog system interface is installed on one of a user device and a thirdparty server, wherein the dialog system is maintained at an onlineplatform; identify that the dialog system interface is associated withthe dialog system; identify at least one dialog system extension elementof the plurality of dialog system extension elements, the at least onedialog system extension element being associated with the dialog system;process the user request by the at least one dialog system extensionelement to generate a response to the user request; and cause deliveryof the response to the end user.
 12. The system of claim 1, wherein theat least one processor is further operable to: upon the receiving of theselection of the one of the plurality of dialog system extensionelements, receive, from the end user, a selection of a subscription planassociated with the one of the plurality of dialog system extensionelements; and receive a payment for the one of the plurality of dialogsystem extension elements, the payment being provided by the end user inaccordance with the subscription plan.
 13. The system of claim 1,wherein the at least one processor is further operable to: receive auser request of the end user from a dialog system interface, wherein thedialog system interface is installed on one of a user device and a thirdparty server, wherein the dialog system is maintained at an onlineplatform; identify that the dialog system interface is associated withthe dialog system; based on the user request, activate the dialog systemand process the user request using the dialog system to generate a firstresponse; identify at least one dialog system extension element of theplurality of dialog system extension elements on the online marketplace,the at least one dialog system extension element being applicable forprocessing the user request; process the user request using the at leastone dialog system extension element to generate a second response to theuser request; and cause delivery of the first response and the secondresponse to the end user, the second response being accompanied with anincentive for the end user to buy the at least one dialog systemextension element.
 14. A computer-implemented method for enhancingfunctionalities of dialog systems, the method being performed by atleast one processor and a memory, the method comprising: maintaining, bythe memory, an online marketplace comprising a plurality of dialogsystem extension elements, wherein each of the plurality of dialogsystem extension elements includes at least one of a dialog systemplugin, a dialog system add-on, a dialog system update, and a dialogsystem upgrade; receiving, by the at least one processor, a selection ofone of the plurality of dialog system extension elements from an enduser, the end user being associated with a dialog system; and based onthe selection, associating, by the at least one processor, the one ofthe plurality of dialog system extension elements with the dialogsystem.
 15. The method of claim 14, wherein the selection includesactivating one or more annotations associated with the one of theplurality of dialog system extension elements, the one or moreannotations embedded into a software application installed on a userdevice and including a code within the software application, wherein theassociating of the one of the plurality of dialog system extensionelements with the dialog system is initiated by the activating of one ormore annotations.
 16. The method of claim 14, further comprising:receiving, by the at least one processor, a user request of the end userfrom a dialog system interface, wherein the dialog system interface isinstalled on one of a user device and a third party server, the dialogsystem interface being associated with the dialog system, wherein thedialog system is maintained at an online platform; based on the userrequest, activating, by the at least one processor, the dialog systemand retrieving at least one or more dialog system entities and one ormore dialog system intents; processing, by the at least one processor,the user request by applying the one or more dialog system entities andthe one or more dialog system intents to generate a response; if theprocessing of the user request is successful, delivering, by the atleast one processor, the response to the end user; and if the processingof the user request is unsuccessful, processing, by the at least oneprocessor, the user request using the one of the plurality of dialogsystem extension elements to generate a substitute response to the userrequest and delivering the substitute response to the end user.
 17. Themethod of claim 14, further comprising: receiving, by the at least oneprocessor, a user request of the end user from a dialog systeminterface, wherein the dialog system interface is installed on one of auser device and a third party server, wherein the dialog system ismaintained at an online platform; identifying, by the at least oneprocessor, that the dialog system interface is associated with thedialog system; identifying, by the at least one processor, at least onedialog system extension element of the plurality of dialog systemextension elements, the at least one dialog system extension elementbeing associated with the dialog system; processing, by the at least oneprocessor, the user request by the at least one dialog system extensionelement to generate a response to the user request; and causing, by theat least one processor, delivery of the response to the end user. 18.The method of claim 14, further comprising: receiving, by the at leastone processor, a user request of the end user from a dialog systeminterface, wherein the dialog system interface is installed on one of auser device and a third party server, wherein the dialog system ismaintained at an online platform; identifying, by the at least oneprocessor, that the dialog system interface is associated with thedialog system; based on the user request, activating, by the at leastone processor, the dialog system and processing, by the at least oneprocessor, the user request using the dialog system to generate a firstresponse; identifying, by the at least one processor, at least onedialog system extension element of the plurality of dialog systemextension elements on the online marketplace, the at least one dialogsystem extension element being applicable for processing the userrequest; processing, by the at least one processor, the user requestusing the at least one dialog system extension element to generate asecond response to the user request; and causing, by the at least oneprocessor, delivery of the first response and the second response to theend user, the second response being accompanied with an incentive forthe end user to buy the at least one dialog system extension element.19. The method of claim 14, further comprising: upon the receiving ofthe selection of the one of the plurality of dialog system extensionelements, receiving, by the at least one processor, from the end user, aselection of a subscription plan associated with the one of theplurality of dialog system extension elements; and receiving, by the atleast one processor, a payment for the one of the plurality of dialogsystem extension elements, the payment being provided by the end user inaccordance with the subscription plan.
 20. A system for enhancing dialogsystems, comprising: a memory operable to maintain an online marketplacecomprising a plurality of dialog system extension elements, wherein eachof the plurality of dialog system extension elements includes at leastone of a dialog system plugin, a dialog system add-on, a dialog systemupdate, and a dialog system upgrade; and at least one processor operableto: receive a selection of one of the plurality of dialog systemextension elements from an end user, the end user being associated witha dialog system; based on the selection, associate the one of theplurality of dialog system extension elements with the dialog systemassociated with the end user, wherein the associating of the one of theplurality of dialog system extension elements with the dialog systemincludes embedding the one of the plurality of dialog system extensionelements into the dialog system; receive a user request of the end userfrom a dialog system interface, wherein the dialog system interface isinstalled on one of a user device and a third party server, wherein thedialog system is maintained at an online platform; identify that thedialog system interface is associated with the dialog system; based onthe user request, activate the dialog system and process the userrequest using the dialog system to generate a first response; identifyat least one dialog system extension element of the plurality of dialogsystem extension elements on the online marketplace, the at least onedialog system extension element being applicable for processing the userrequest; process the user request using the at least one dialog systemextension element to generate a second response to the user request; andcause delivery of the first response and the second response to the enduser, the second response being accompanied with an incentive for theend user to buy the at least one dialog system extension element.